From 5d8bf2503f536d21c22302f3820e48665fddcd74 Mon Sep 17 00:00:00 2001 From: robertl Date: Fri, 18 Apr 2008 05:41:12 +0000 Subject: [PATCH] Numerous doc enhancements. (Left off with filters.) --- xmldoc/chapters/preface.xml | 8 ++--- xmldoc/chapters/styles.xml | 12 ++++---- xmldoc/chapters/use.xml | 30 +++++++++++++++---- xmldoc/formats/destinator_itn.xml | 1 + xmldoc/formats/destinator_poi.xml | 1 + xmldoc/formats/destinator_trk.xml | 1 + xmldoc/formats/g7towin.xml | 2 +- xmldoc/formats/ggv_log.xml | 2 +- xmldoc/formats/google.xml | 2 +- xmldoc/formats/ik3d.xml | 3 ++ xmldoc/formats/kml.xml | 26 ++++++++++++++-- xmldoc/formats/ktf2.xml | 4 +-- xmldoc/formats/msroute.xml | 4 ++- xmldoc/formats/msroute1.xml | 4 ++- xmldoc/formats/mtk-bin.xml | 8 ++--- xmldoc/formats/navilink.xml | 2 +- xmldoc/formats/options/garmin-resettime.xml | 11 ++++++- xmldoc/formats/options/garmin_gpi-sleep.xml | 6 ++-- xmldoc/formats/options/gdb-roadbook.xml | 6 ++-- xmldoc/formats/options/gpx-logpoint.xml | 7 ++++- xmldoc/formats/options/gpx-snlen.xml | 4 ++- xmldoc/formats/options/gpx-suppresswhite.xml | 4 ++- xmldoc/formats/options/gpx-urlbase.xml | 3 ++ xmldoc/formats/options/magellan-deficon.xml | 4 ++- xmldoc/formats/options/magellanx-deficon.xml | 4 ++- .../formats/options/navicache-noretired.xml | 4 ++- xmldoc/formats/options/ozi-proximity.xml | 5 +++- xmldoc/formats/options/ozi-snlen.xml | 4 ++- xmldoc/formats/options/ozi-snunique.xml | 4 ++- xmldoc/formats/options/ozi-snupper.xml | 4 ++- xmldoc/formats/options/ozi-snwhite.xml | 4 ++- xmldoc/formats/options/ozi-wptbgcolor.xml | 4 ++- xmldoc/formats/options/ozi-wptfgcolor.xml | 4 ++- xmldoc/formats/options/pathaway-deficon.xml | 4 ++- xmldoc/formats/options/pathaway-snlen.xml | 4 ++- xmldoc/formats/options/pcx-cartoexploreur.xml | 5 +++- xmldoc/formats/options/pcx-deficon.xml | 4 ++- xmldoc/formats/options/wfff-ahcicon.xml | 4 ++- xmldoc/formats/options/wfff-ahoicon.xml | 3 ++ xmldoc/formats/options/wfff-aicicon.xml | 4 ++- xmldoc/formats/options/wfff-aioicon.xml | 3 ++ xmldoc/formats/options/wfff-snmac.xml | 4 ++- xmldoc/formats/osm.xml | 4 +-- xmldoc/formats/s_and_t.xml | 7 +++-- xmldoc/formats/unicsv.xml | 3 +- xmldoc/formats/wfff.xml | 2 +- 46 files changed, 178 insertions(+), 65 deletions(-) create mode 100644 xmldoc/formats/destinator_itn.xml create mode 100644 xmldoc/formats/destinator_poi.xml create mode 100644 xmldoc/formats/destinator_trk.xml create mode 100644 xmldoc/formats/ik3d.xml diff --git a/xmldoc/chapters/preface.xml b/xmldoc/chapters/preface.xml index 71c0293e5..eba95ebc0 100644 --- a/xmldoc/chapters/preface.xml +++ b/xmldoc/chapters/preface.xml @@ -7,14 +7,14 @@ to hold waypoint, track, and route information in various programs used by computers and GPS receivers. GPX defines a standard in XML to contain all the data, but there are too many -programs that don't understand it yet and too much data that are in an +programs that don't understand it yet and too much data in alternate formats. -Perhaps you have an Explorist 600 and your friend has a StreetPilot 2720. +Perhaps you have an Explorist 600 and your friend has a StreetPilot 2720. You've collected a a list of your favorite locations as waypoints and you'd -like to be able to share them. Unfortunately, his copy of Garmin Mapsource -won't read data created by your copy of Magellan Directroute. What you need +like to be able to share them. Unfortunately, his copy of Garmin Mapsource +won't read data created by your copy of Magellan Mapsend DirectRoute. What you need is a program that converts data bewteen the two programs. diff --git a/xmldoc/chapters/styles.xml b/xmldoc/chapters/styles.xml index 2f7e2e9c7..4223913a2 100644 --- a/xmldoc/chapters/styles.xml +++ b/xmldoc/chapters/styles.xml @@ -1182,37 +1182,37 @@ example:
STREET_NAME -Street address including house number. +Street address including house number. Notice that this is not used for any geocoding, it's merely textual description associated with a position. example:STREET_ADDR, "", "%s"
CITY -The name of a city. Sometimes part of "Points of Interest". +The name of a city. Sometimes part of "Points of Interest". This is simple textual data associated with a position, no geocoding will be done.. example:CITY, "", "%s"
COUNTRY -....... +The name of a country associated with a position. example:COUNTRY, "", "%s"
FACILITY -....... +The name of a facility to associate with a position. example:FACILITY, "", "%s"
PHONE_NR -....... +A phone number associated with a position. This is just textual data attached for convenience. example:PHONE_NR, "", "%s"
POSTAL_CODE -....... +A postal code to associate with a position. It is freeform text and is not used by GPSBabel for any geocoding or such. example:POSTAL_CODE, "", "%s"
diff --git a/xmldoc/chapters/use.xml b/xmldoc/chapters/use.xml index 29145d863..6c5a2970b 100644 --- a/xmldoc/chapters/use.xml +++ b/xmldoc/chapters/use.xml @@ -68,9 +68,15 @@ name of a file to be read or written. This command will read from a Magellan unit attached to the first serial port on a Linux system (device names will vary on other OSes; typically COMx: on WIndows) and write them as a geocaching loc file. + + Command showing Linux download from Magellan serial and writing to .loc file gpsbabel -i magellan -f /dev/ttyS0 -o geo -F mag.loc + This second command does the same on Microsoft Windows. + + Command showing Windows download from Magellan serial and writing to .loc file gpsbabel -i magellan -f com1 -o geo -F mag.loc + Optionally, you may specify -s in any command line. This causes the program to ignore any "short" names that may be present in the source data format and synthesize one from the @@ -128,19 +134,28 @@ through when executed. Normally one would: but GPSBabel is flexible enough to allow more complicated operations such as reading from several files (potentially of -different types), applying a filter, reading more data, then write the +different types), applying a filter, reading more data, then writing the merged data to multiple destinations. The input file type remains unchanged until a new -i argument is seen. Files are read in the order they appear. So you could merge three input files into one output file with: - gpsbabel -i geo -f 1.loc -f 2.loc -f 3.loc -o geo -F big.loc + + Merging multiple files into one + gpsbabel -i geo -f 1.loc -f 2.loc -f 3.loc -o geo -F big.loc + You can merge files of different types: - gpsbabel -i geo -f 1.loc -i gpx -f 2.gpx -i pcx 3.pcx --o gpsutil -F big.gps + + Merging multiple files of differing types. + gpsbabel -i geo -f 1.loc -i gpx -f 2.gpx -i pcx 3.pcx -o gpsutil -F big.gps + + + Writing the same data in multiple output formats. You can write the same data in different output formats: + gpsbabel -i geo -f 1.loc -o gpx -F 1.gpx -o pcx -F 1.wpt + If you want to change the character set of input or/and output side you can do this with the option . You can get a complete list @@ -227,13 +242,13 @@ merged data to multiple destinations. There are three optional sections. - "Common format settings" + Common format settings. Any option from any of the formats listed here will be used by GPSBabel unless explictly provided on the command line. - "Common filter settings" + Common filter settings. As above, but for filters. @@ -277,7 +292,10 @@ merged data to multiple destinations. output. Additional formats may be added by interested parties later. + + Read realtime positioning from Garmin USB, write to Keyhole Markup gpsbabel -T -i garmin -f usb: -o kml -F xxx.kml + Will read the USB-connected Garmin and rewrite 'xxx.kml' atomically, suitable for a self-refreshing network link in Google Earth. diff --git a/xmldoc/formats/destinator_itn.xml b/xmldoc/formats/destinator_itn.xml new file mode 100644 index 000000000..8b1378917 --- /dev/null +++ b/xmldoc/formats/destinator_itn.xml @@ -0,0 +1 @@ + diff --git a/xmldoc/formats/destinator_poi.xml b/xmldoc/formats/destinator_poi.xml new file mode 100644 index 000000000..8b1378917 --- /dev/null +++ b/xmldoc/formats/destinator_poi.xml @@ -0,0 +1 @@ + diff --git a/xmldoc/formats/destinator_trk.xml b/xmldoc/formats/destinator_trk.xml new file mode 100644 index 000000000..8b1378917 --- /dev/null +++ b/xmldoc/formats/destinator_trk.xml @@ -0,0 +1 @@ + diff --git a/xmldoc/formats/g7towin.xml b/xmldoc/formats/g7towin.xml index e548a6375..db734eb4c 100644 --- a/xmldoc/formats/g7towin.xml +++ b/xmldoc/formats/g7towin.xml @@ -1,5 +1,5 @@ - Like GPSBabel G7ToWin is a program which allows uploading and + Like GPSBabel, G7ToWin is a program which allows uploading and downloading information from several GPS devices (Garmin, Lowrance/Eagle, Magellan). G7ToWin has its own data format, which is an enhanced format used in Gardown. diff --git a/xmldoc/formats/ggv_log.xml b/xmldoc/formats/ggv_log.xml index a3ab06f3d..9b76cc725 100644 --- a/xmldoc/formats/ggv_log.xml +++ b/xmldoc/formats/ggv_log.xml @@ -7,6 +7,6 @@ We can also read some GPS data (including coordinates) from version 2.5. But - it seems, that this newer version doesn't more store time stamps. This can be + it seems, that this newer version no longer stores time stamps. This can be a problem when converting to other formats or if you want to use our track filter. diff --git a/xmldoc/formats/google.xml b/xmldoc/formats/google.xml index d458c7cb1..62155c169 100644 --- a/xmldoc/formats/google.xml +++ b/xmldoc/formats/google.xml @@ -2,7 +2,7 @@ This format is designed to read the XML emitted when you -tack "&output=js" onto the end of a Google Mapsroute URL (use +tack "&output=js" onto the end of a Google Maps route URL (use the "link to this page" option to get a usable URL.) This allows you to plan a route using Google Maps, then download it and use it in your own mapping program or GPS receiver. To get a file suitable for use diff --git a/xmldoc/formats/ik3d.xml b/xmldoc/formats/ik3d.xml new file mode 100644 index 000000000..f81b5db75 --- /dev/null +++ b/xmldoc/formats/ik3d.xml @@ -0,0 +1,3 @@ + +This is the format for MagicMaps project ikt files + diff --git a/xmldoc/formats/kml.xml b/xmldoc/formats/kml.xml index 1e350a721..e51a42573 100644 --- a/xmldoc/formats/kml.xml +++ b/xmldoc/formats/kml.xml @@ -1,8 +1,15 @@ KML, the Keyhole Markup Language, is used by Keyhole and -Google Earth. There are numerous -features in this file format that GPSBabel -doesn't support - such as camera views - but core spport waypoints, tracks, and routes work well. +Google Earth. + +There are concepts in KML that GPSBabel can't support very well on +read becuase they don't map well into other programs. For example, KML has +ideas of camera views and names and descriptions can have arbitrarily +complicated HTML in them. KML files may have tiered "Styles" which +can identify sizing info and URLs of associated icons. Reading such +files with GPSBabel - even if your goal it to out to KML - can often +have suprising results. Simple files with waypoints and paths (which +GPSBabel represents internally as tracks) work fine. Google Earth also uses GPSBabel internally for receiver communications @@ -11,3 +18,16 @@ and several file format imports and exports. In general, GPSBabel's KML writer is relatively strong. GPSBabel handles simple KML on read fairly well, but if you're dealing with handcrafted KML that uses extensive features that have no analog in other formats like nested folders, ringgeometry, camera angles, and such, don't expect GPSBabel to do well with them on read. + + Google Earth 4.0 and later have a feature that can suprise users of this + format. Earth's "time slider" feature controls what timestamped data + gets displayed. If you're using data that has timestampes (e.g. GPX + points that contain time or almost any track data) this will be important + to you. The time slider defaults to the far left position and fully closed. + This means that only the first data point will be displayed. You can + tweak Earth's settings to "view->show time->never" or + you can widen the time slider to show the range of data of interest. + + + See Google Earth's documentation on timelines for more info. + diff --git a/xmldoc/formats/ktf2.xml b/xmldoc/formats/ktf2.xml index 2ace12f66..31fd17dbf 100644 --- a/xmldoc/formats/ktf2.xml +++ b/xmldoc/formats/ktf2.xml @@ -1,5 +1,3 @@ - - - Support for Kartex 5 trackfiles. For more info see kwf2. + Support for Kartex 5 trackfiles. For more info see kwf2. diff --git a/xmldoc/formats/msroute.xml b/xmldoc/formats/msroute.xml index 699384c5b..d1d4d36b2 100644 --- a/xmldoc/formats/msroute.xml +++ b/xmldoc/formats/msroute.xml @@ -2,7 +2,9 @@ Input support for Microsoft AutoRoute 2002-2006 .axe files -and Microsoft Streets and Trips .est files. +and Microsoft Streets and Trips .est files. This is for reading routes +created this program and is different than the +s_and_t format used for writing pushpins. These files contains only routes. We can extract the coordinates and the names of the points within route. An export to this format will not be supported. diff --git a/xmldoc/formats/msroute1.xml b/xmldoc/formats/msroute1.xml index 699384c5b..d1d4d36b2 100644 --- a/xmldoc/formats/msroute1.xml +++ b/xmldoc/formats/msroute1.xml @@ -2,7 +2,9 @@ Input support for Microsoft AutoRoute 2002-2006 .axe files -and Microsoft Streets and Trips .est files. +and Microsoft Streets and Trips .est files. This is for reading routes +created this program and is different than the +s_and_t format used for writing pushpins. These files contains only routes. We can extract the coordinates and the names of the points within route. An export to this format will not be supported. diff --git a/xmldoc/formats/mtk-bin.xml b/xmldoc/formats/mtk-bin.xml index 940283630..6d5b0578b 100644 --- a/xmldoc/formats/mtk-bin.xml +++ b/xmldoc/formats/mtk-bin.xml @@ -1,11 +1,11 @@ Binary file protocol converter for MTK based GPS loggers. This format reads the raw binary format created by the MTK Windows application -and outputs to other gpsbabel supported formats. -When using the csv option a MTK application compatible output file will also be created. - +and outputs to other formats supported by GPSBabel +When using the csv option a MTK application compatible output file will also be created. + It has been tested with Transystem i-Blue 747 but other devices should work as well (Qstarz BT-Q1000, iTrek Z1, ...) - + All position items (including button push) will be listed as trackpoints in the output. Log items due to button push are presented as waypoints. In theory we would not add waypoints to the list of trackpoints. But as the MTK logger restart the diff --git a/xmldoc/formats/navilink.xml b/xmldoc/formats/navilink.xml index fadfd8154..aae598562 100644 --- a/xmldoc/formats/navilink.xml +++ b/xmldoc/formats/navilink.xml @@ -2,7 +2,7 @@ GPSBabel supports the Navilink protocol used by the Locosys GT-11 GPS receivers. These are sold under a variety of names including: - + NaviGPS NaviGPS-BT GT-11 diff --git a/xmldoc/formats/options/garmin-resettime.xml b/xmldoc/formats/options/garmin-resettime.xml index 8b1378917..151a43f7a 100644 --- a/xmldoc/formats/options/garmin-resettime.xml +++ b/xmldoc/formats/options/garmin-resettime.xml @@ -1 +1,10 @@ - + + This option is experimental and was added to solve a very specific problem. + Certain Garmin units (the original black and white Vista is known to have + this) will sometimes scramble their clock crazy far into the future (like + 2066). When this happens, the GPS itself may or may not work and + later conversations with GPSBabel may fail as the time overflows the + documented range. The use of brings the GPS's internal clock + back close enough to reality that the GPS itself can then "fix" it when + it has next a lock. + diff --git a/xmldoc/formats/options/garmin_gpi-sleep.xml b/xmldoc/formats/options/garmin_gpi-sleep.xml index 5707e3a16..094fb5f9e 100644 --- a/xmldoc/formats/options/garmin_gpi-sleep.xml +++ b/xmldoc/formats/options/garmin_gpi-sleep.xml @@ -1,11 +1,11 @@ - Garmin unit seems to use the creation timestamp of GPI files for internal purposes. + The Garmin units seem to use the creation timestamp of GPI files for internal purposes. In other words, if you load GPI files with same creation timestamp on your device, - strange things will happen (missing or repeated POIs). With the sleep option, GPSbabel waits a given + strange things will happen, such as having missing or repeated POIs. With the sleep option, GPSBabel waits a given number of seconds after the GPI file was written. - In the normal case of using GPSBabel from commandline or from the GUI, the chance of creating files + In the normal case of using GPSBabel from the command line or from the GUI, the chance of creating files with the same timestamp is in the nearly ZERO. In scripts or batch files where you are writing multiple files - even from different GPSBabel instances - the odds of this happening is rather good. The sleep option forces GPSBabel to wait after creating a file to ensure the timestamps are unique. Values are specified in seconds and can be 1 or more. diff --git a/xmldoc/formats/options/gdb-roadbook.xml b/xmldoc/formats/options/gdb-roadbook.xml index 76ac5ddf8..296d7b03f 100644 --- a/xmldoc/formats/options/gdb-roadbook.xml +++ b/xmldoc/formats/options/gdb-roadbook.xml @@ -12,8 +12,8 @@ - Because gdb creates internal a route AND a waypoint list, you have to drop all - waypoints and transform the route into waypoints. So you'll get a well ordered - html output. We sugess these steps for all waypoint-only formats as html. + Because gdb internally creates a route AND a waypoint list, you have to drop all + waypoints and transform the route into waypoints in order to get a well ordered + html output. We suggest these steps for all waypoint-only formats as html. diff --git a/xmldoc/formats/options/gpx-logpoint.xml b/xmldoc/formats/options/gpx-logpoint.xml index 8b1378917..2739b4889 100644 --- a/xmldoc/formats/options/gpx-logpoint.xml +++ b/xmldoc/formats/options/gpx-logpoint.xml @@ -1 +1,6 @@ - + + When reading Groundspeak Pocket Queries , the option creates additional waypoints from the log entries. + + + A typical use for this is to get coordinates read from "corrected coordinates" logs. + diff --git a/xmldoc/formats/options/gpx-snlen.xml b/xmldoc/formats/options/gpx-snlen.xml index 8b1378917..999bb2589 100644 --- a/xmldoc/formats/options/gpx-snlen.xml +++ b/xmldoc/formats/options/gpx-snlen.xml @@ -1 +1,3 @@ - + + When used with the to control shortnames, the snlen suboption to GPX controls how long the generated smartname will be. This can be useful for cases like writing GPX files to a GPS that has a fixed waypoint name length. + diff --git a/xmldoc/formats/options/gpx-suppresswhite.xml b/xmldoc/formats/options/gpx-suppresswhite.xml index 8b1378917..e5fc04063 100644 --- a/xmldoc/formats/options/gpx-suppresswhite.xml +++ b/xmldoc/formats/options/gpx-suppresswhite.xml @@ -1 +1,3 @@ - + +When used with the to generate smart shortnames, this suboption controls whether whitespace is allowed in the generated shortnames. + diff --git a/xmldoc/formats/options/gpx-urlbase.xml b/xmldoc/formats/options/gpx-urlbase.xml index 8b1378917..fefa663cf 100644 --- a/xmldoc/formats/options/gpx-urlbase.xml +++ b/xmldoc/formats/options/gpx-urlbase.xml @@ -1 +1,4 @@ + + This is a fairly esoteric option. If the GPX file you are reading has only base pathnames (e.g "foo.html") the value you specify to this argument will be prepended to that. For example, "-o gpx,urlbase=c:\My Documents\Whatever" would result in the link to that waypoint being written to refer to c:\My Document\WHatever\foo.html + diff --git a/xmldoc/formats/options/magellan-deficon.xml b/xmldoc/formats/options/magellan-deficon.xml index 8b1378917..5e05476af 100644 --- a/xmldoc/formats/options/magellan-deficon.xml +++ b/xmldoc/formats/options/magellan-deficon.xml @@ -1 +1,3 @@ - + + The deficon option is used to control the icon output when writing to this format. It overrides any icon informatino that might be present in the source data. + diff --git a/xmldoc/formats/options/magellanx-deficon.xml b/xmldoc/formats/options/magellanx-deficon.xml index 8b1378917..5e05476af 100644 --- a/xmldoc/formats/options/magellanx-deficon.xml +++ b/xmldoc/formats/options/magellanx-deficon.xml @@ -1 +1,3 @@ - + + The deficon option is used to control the icon output when writing to this format. It overrides any icon informatino that might be present in the source data. + diff --git a/xmldoc/formats/options/navicache-noretired.xml b/xmldoc/formats/options/navicache-noretired.xml index 8b1378917..e93b2e21c 100644 --- a/xmldoc/formats/options/navicache-noretired.xml +++ b/xmldoc/formats/options/navicache-noretired.xml @@ -1 +1,3 @@ - + + If this option is present, retired (archived) caches will be suppressed on write. + diff --git a/xmldoc/formats/options/ozi-proximity.xml b/xmldoc/formats/options/ozi-proximity.xml index 8b1378917..650aad86b 100644 --- a/xmldoc/formats/options/ozi-proximity.xml +++ b/xmldoc/formats/options/ozi-proximity.xml @@ -1 +1,4 @@ - + + This option, specified in meters, allows you to set the proximity of +written in waypoints. + diff --git a/xmldoc/formats/options/ozi-snlen.xml b/xmldoc/formats/options/ozi-snlen.xml index 8b1378917..f7eb60b14 100644 --- a/xmldoc/formats/options/ozi-snlen.xml +++ b/xmldoc/formats/options/ozi-snlen.xml @@ -1 +1,3 @@ - + + This option allows you to specify the length of waypoint names written to this format when used with the option. + diff --git a/xmldoc/formats/options/ozi-snunique.xml b/xmldoc/formats/options/ozi-snunique.xml index 8b1378917..1e83a5d92 100644 --- a/xmldoc/formats/options/ozi-snunique.xml +++ b/xmldoc/formats/options/ozi-snunique.xml @@ -1 +1,3 @@ - + + When specified, this option will force the generated waypoint names to be unique. + diff --git a/xmldoc/formats/options/ozi-snupper.xml b/xmldoc/formats/options/ozi-snupper.xml index 8b1378917..608e6bb2f 100644 --- a/xmldoc/formats/options/ozi-snupper.xml +++ b/xmldoc/formats/options/ozi-snupper.xml @@ -1 +1,3 @@ - + + When specified, this option will force generated shortnames to be in all uppercase letters. + diff --git a/xmldoc/formats/options/ozi-snwhite.xml b/xmldoc/formats/options/ozi-snwhite.xml index 8b1378917..80b964efa 100644 --- a/xmldoc/formats/options/ozi-snwhite.xml +++ b/xmldoc/formats/options/ozi-snwhite.xml @@ -1 +1,3 @@ - + + This option forces waypoint names generated with to allow whitespace in the names. + diff --git a/xmldoc/formats/options/ozi-wptbgcolor.xml b/xmldoc/formats/options/ozi-wptbgcolor.xml index 8b1378917..0b5fa134a 100644 --- a/xmldoc/formats/options/ozi-wptbgcolor.xml +++ b/xmldoc/formats/options/ozi-wptbgcolor.xml @@ -1 +1,3 @@ - + + This option allows you to specify a background color of a waypoint. You can specify it as either a decimal number or one of the standard web colors. + diff --git a/xmldoc/formats/options/ozi-wptfgcolor.xml b/xmldoc/formats/options/ozi-wptfgcolor.xml index 8b1378917..fbaa20a8c 100644 --- a/xmldoc/formats/options/ozi-wptfgcolor.xml +++ b/xmldoc/formats/options/ozi-wptfgcolor.xml @@ -1 +1,3 @@ - + + This option allows you to specify a foreground color of a waypoint. You can specify it as either a decimal number or one of the standard web colors. + diff --git a/xmldoc/formats/options/pathaway-deficon.xml b/xmldoc/formats/options/pathaway-deficon.xml index 8b1378917..5e05476af 100644 --- a/xmldoc/formats/options/pathaway-deficon.xml +++ b/xmldoc/formats/options/pathaway-deficon.xml @@ -1 +1,3 @@ - + + The deficon option is used to control the icon output when writing to this format. It overrides any icon informatino that might be present in the source data. + diff --git a/xmldoc/formats/options/pathaway-snlen.xml b/xmldoc/formats/options/pathaway-snlen.xml index 8b1378917..f7eb60b14 100644 --- a/xmldoc/formats/options/pathaway-snlen.xml +++ b/xmldoc/formats/options/pathaway-snlen.xml @@ -1 +1,3 @@ - + + This option allows you to specify the length of waypoint names written to this format when used with the option. + diff --git a/xmldoc/formats/options/pcx-cartoexploreur.xml b/xmldoc/formats/options/pcx-cartoexploreur.xml index 8b1378917..17bc9721b 100644 --- a/xmldoc/formats/options/pcx-cartoexploreur.xml +++ b/xmldoc/formats/options/pcx-cartoexploreur.xml @@ -1 +1,4 @@ - + + Carto Exploreur requires a slightly incompatible variation of the PCX format +when written. Specifying this option on write tells us to create that strain of PCX. + diff --git a/xmldoc/formats/options/pcx-deficon.xml b/xmldoc/formats/options/pcx-deficon.xml index 8b1378917..5e05476af 100644 --- a/xmldoc/formats/options/pcx-deficon.xml +++ b/xmldoc/formats/options/pcx-deficon.xml @@ -1 +1,3 @@ - + + The deficon option is used to control the icon output when writing to this format. It overrides any icon informatino that might be present in the source data. + diff --git a/xmldoc/formats/options/wfff-ahcicon.xml b/xmldoc/formats/options/wfff-ahcicon.xml index 8b1378917..35d45508d 100644 --- a/xmldoc/formats/options/wfff-ahcicon.xml +++ b/xmldoc/formats/options/wfff-ahcicon.xml @@ -1 +1,3 @@ - + +This options lets you specify an icon for an Ad-hoc, closed, waypoint. + diff --git a/xmldoc/formats/options/wfff-ahoicon.xml b/xmldoc/formats/options/wfff-ahoicon.xml index 8b1378917..5961bdc10 100644 --- a/xmldoc/formats/options/wfff-ahoicon.xml +++ b/xmldoc/formats/options/wfff-ahoicon.xml @@ -1 +1,4 @@ + +This options lets you specify an icon for an Ad-hoc, open, waypoint. + diff --git a/xmldoc/formats/options/wfff-aicicon.xml b/xmldoc/formats/options/wfff-aicicon.xml index 8b1378917..4fe063f52 100644 --- a/xmldoc/formats/options/wfff-aicicon.xml +++ b/xmldoc/formats/options/wfff-aicicon.xml @@ -1 +1,3 @@ - + +This option lets you specify an icon for infrastructure closed points. + diff --git a/xmldoc/formats/options/wfff-aioicon.xml b/xmldoc/formats/options/wfff-aioicon.xml index 8b1378917..9bba54594 100644 --- a/xmldoc/formats/options/wfff-aioicon.xml +++ b/xmldoc/formats/options/wfff-aioicon.xml @@ -1 +1,4 @@ + +This option lets you specify an icon for infrastructure open points. + diff --git a/xmldoc/formats/options/wfff-snmac.xml b/xmldoc/formats/options/wfff-snmac.xml index 8b1378917..d8ad46984 100644 --- a/xmldoc/formats/options/wfff-snmac.xml +++ b/xmldoc/formats/options/wfff-snmac.xml @@ -1 +1,3 @@ - + + This options lets you specify that the shortname of the waypoint is the MAC address. + diff --git a/xmldoc/formats/osm.xml b/xmldoc/formats/osm.xml index 45c59419d..9ebc8ed62 100644 --- a/xmldoc/formats/osm.xml +++ b/xmldoc/formats/osm.xml @@ -5,9 +5,9 @@ These data files are XML based. Every GPS element (way or node) described by the files has a unique number as identifier. When we write OSM data files and don't know something about the id's, - negative numbers will be used as identifier. This has beed tested with JOSM. + negative numbers will be used as identifier. This has been tested with JOSM. - Because the resulting timestamps of OSM ways aren't in the manner of real GPS track, + Because the resulting timestamps of OSM ways differ from real GPS tracks, we read OSM ways into routes. On the output side we write all available routes and tracks into the osm target file. diff --git a/xmldoc/formats/s_and_t.xml b/xmldoc/formats/s_and_t.xml index 1b82e49c4..2eb0956e1 100644 --- a/xmldoc/formats/s_and_t.xml +++ b/xmldoc/formats/s_and_t.xml @@ -1,10 +1,13 @@ - This is a format for importing into + This is a format for creating data to be read by Microsoft Streets and -Trips. It's been exercised on versions from 2003 through 2007. Detailed +Trips. It's been exercised on versions from 2003 through 2008. Detailed instructions on how to use it, including preserving hyperlinks, are at gpsbabel.org + + This format has nothing to do with the .est/axe format used by this program to store routes. + diff --git a/xmldoc/formats/unicsv.xml b/xmldoc/formats/unicsv.xml index 02f0b182d..d3162b52c 100644 --- a/xmldoc/formats/unicsv.xml +++ b/xmldoc/formats/unicsv.xml @@ -1,6 +1,7 @@ Unicsv examines the first line of a file to determine the field - order and field separator in that file. It is thus read-only format. + order and field separator in that file. On write, it tries to + figure out what data it has and writes headers and all the data it can. If the first line contains any tabs, the data lines are assumed diff --git a/xmldoc/formats/wfff.xml b/xmldoc/formats/wfff.xml index 5e808900e..ac5ebaf1f 100644 --- a/xmldoc/formats/wfff.xml +++ b/xmldoc/formats/wfff.xml @@ -1,7 +1,7 @@ - WFFF is the export format for Aspecto Software's WiFiFoFum 2.0 for Windows Mobile PCs. + WFFF is the export format for Aspecto Software's WiFiFoFum 2.0 for Windows Mobile PCs. It is a simple XML format that is read-only to GPSBabel and stores information about a WiFi stumbling session. All WiFi-specific elements are written in the description field, similar to the netstumbler format. -- 2.30.2